Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29618690fecf7a03016208d53141ec4b5be03ee36c05e2b0db6be47cecf5333b

Tx prefix hash: e1358bb0d49c8feb7ef9a367ea2e44438bb2463ff3df8356c805977c1974034a
Tx public key: c445c80931c183bd6819a4f3765a74e2f50a47c63eebac3cdcf652469aeb7bf9
Timestamp: 1758355542 Timestamp [UTC]: 2025-09-20 08:05:42 Age [y:d:h:m:s]: 00:236:00:58:19
Block: 1372431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161057 RingCT/type: yes/0
Extra: 01c445c80931c183bd6819a4f3765a74e2f50a47c63eebac3cdcf652469aeb7bf9021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6874dabea36cf46ab24e76fd3d0a55bfb3cc9e71eec48689f230d8564ef1f8ca 0.000600000000 1860516 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": 1372441, "vin": [ { "gen": { "height": 1372431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6874dabea36cf46ab24e76fd3d0a55bfb3cc9e71eec48689f230d8564ef1f8ca" } } ], "extra": [ 1, 196, 69, 200, 9, 49, 193, 131, 189, 104, 25, 164, 243, 118, 90, 116, 226, 245, 10, 71, 198, 62, 235, 172, 60, 220, 246, 82, 70, 154, 235, 123, 249, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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: