Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd94db67a36120ff2cb226077c876d731b5d6ffde4710948954cd282220ac68d

Tx prefix hash: fb9f4dd64d38059a90d83525c233cee148618d7a0001ca5bc4157b5ee5ca0a5f
Tx public key: 4d8c3137674047e5a75b5ee2c3d19efdec384fe0cf3087d13f3601098fb85918
Timestamp: 1577890825 Timestamp [UTC]: 2020-01-01 15:00:25 Age [y:d:h:m:s]: 06:131:07:19:51
Block: 36392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1494997 RingCT/type: yes/0
Extra: 014d8c3137674047e5a75b5ee2c3d19efdec384fe0cf3087d13f3601098fb8591802110000001d4ac5aa02000000000000000000

1 output(s) for total of 0.464971731396 xmr

stealth address amount amount idx tag
00: 35857d7cfb7177d3cc4cf082662000f654f38820c4d2290af7edf975a349c237 0.464971731396 61640 of 0 -

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": 36402, "vin": [ { "gen": { "height": 36392 } } ], "vout": [ { "amount": 464971731396, "target": { "key": "35857d7cfb7177d3cc4cf082662000f654f38820c4d2290af7edf975a349c237" } } ], "extra": [ 1, 77, 140, 49, 55, 103, 64, 71, 229, 167, 91, 94, 226, 195, 209, 158, 253, 236, 56, 79, 224, 207, 48, 135, 209, 63, 54, 1, 9, 143, 184, 89, 24, 2, 17, 0, 0, 0, 29, 74, 197, 170, 2, 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: