Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9215924900ad7d937f6b856882ab25ee267f3a92f9edcc8a5a6ccc44f793182a

Tx prefix hash: 9c9a9255183de1e4911173b8b4e41a0a276951249407b2c5cc310d005deaeb01
Tx public key: 5f8757b862060f348c070ea7e897f93223663f18a9d2461ffa2d7fa4b146d240
Timestamp: 1743325293 Timestamp [UTC]: 2025-03-30 09:01:33 Age [y:d:h:m:s]: 00:320:22:57:43
Block: 1250442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227046 RingCT/type: yes/0
Extra: 015f8757b862060f348c070ea7e897f93223663f18a9d2461ffa2d7fa4b146d2400211000000051a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a6aae8670346c6ffb7015c538cfdd5e9590316887202e07074f505165766a3c1 0.000600000000 1737491 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": 1250452, "vin": [ { "gen": { "height": 1250442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6aae8670346c6ffb7015c538cfdd5e9590316887202e07074f505165766a3c1" } } ], "extra": [ 1, 95, 135, 87, 184, 98, 6, 15, 52, 140, 7, 14, 167, 232, 151, 249, 50, 35, 102, 63, 24, 169, 210, 70, 31, 250, 45, 127, 164, 177, 70, 210, 64, 2, 17, 0, 0, 0, 5, 26, 151, 4, 3, 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) | dinastycoin version: tesla-369