Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0342e5a6455bf5400fe08601f2bb9af9458ae190594a018b94bb8fea75dda7ce

Tx prefix hash: 39c0f52678be7f866ee3a0e55b955e8cd19c96b585224e9a3e556186c3f39e3c
Tx public key: 875a2ea123bf360ef951e1153dea10de1b44d3dbd24f27f1f22cd215072cc17b
Timestamp: 1746932145 Timestamp [UTC]: 2025-05-11 02:55:45 Age [y:d:h:m:s]: 01:107:15:46:23
Block: 1280306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341297 RingCT/type: yes/0
Extra: 01875a2ea123bf360ef951e1153dea10de1b44d3dbd24f27f1f22cd215072cc17b0211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a9d57ab7d780dcf98087c167959f7eb00806dea89017478cba6050b7d59c8af7 0.000600000000 1767689 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1280316, "vin": [ { "gen": { "height": 1280306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9d57ab7d780dcf98087c167959f7eb00806dea89017478cba6050b7d59c8af7" } } ], "extra": [ 1, 135, 90, 46, 161, 35, 191, 54, 14, 249, 81, 225, 21, 61, 234, 16, 222, 27, 68, 211, 219, 210, 79, 39, 241, 242, 44, 210, 21, 7, 44, 193, 123, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: