Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f68f5cbe38e1a8b250712f5c82d0f8f034e545c99b6ba20ebae14b80819b4804

Tx prefix hash: bb2ab603c8ad710a4a1a7df65400944abf563f8d05838593f14e29baff0cc5cd
Tx public key: 8184428d6ad0e03fd54f7f4a728ace1a50fef31db0cfad86fc20ac1c992cbcd7
Timestamp: 1774975363 Timestamp [UTC]: 2026-03-31 16:42:43 Age [y:d:h:m:s]: 00:233:22:19:49
Block: 1509914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172856 RingCT/type: yes/0
Extra: 018184428d6ad0e03fd54f7f4a728ace1a50fef31db0cfad86fc20ac1c992cbcd7021100000002ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 380fd16169c8c75ef466d8ccf659f97b1d364e9fca610fcb7aa4b2275621da16 0.000600000000 1999690 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": 1509924, "vin": [ { "gen": { "height": 1509914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "380fd16169c8c75ef466d8ccf659f97b1d364e9fca610fcb7aa4b2275621da16" } } ], "extra": [ 1, 129, 132, 66, 141, 106, 208, 224, 63, 213, 79, 127, 74, 114, 138, 206, 26, 80, 254, 243, 29, 176, 207, 173, 134, 252, 32, 172, 28, 153, 44, 188, 215, 2, 17, 0, 0, 0, 2, 238, 75, 113, 129, 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: