Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46bc9e163e7903bab21dc457bc8c96307babccac0318a9fd910de72fd0841297

Tx prefix hash: 196ae1f79ebf36ea0bd29547ed62289e098d0d16d222617d7451d94690d8e818
Tx public key: dc6d0251724054ec8eee844890f2a09b58b34a3f3b8a444da70f8df2ac97b711
Timestamp: 1579671192 Timestamp [UTC]: 2020-01-22 05:33:12 Age [y:d:h:m:s]: 06:119:01:54:13
Block: 50629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1487475 RingCT/type: yes/0
Extra: 01dc6d0251724054ec8eee844890f2a09b58b34a3f3b8a444da70f8df2ac97b71102110000004d391a8d0e000000000000000000

1 output(s) for total of 0.417105520576 xmr

stealth address amount amount idx tag
00: aec04e0c7126478273e05ba76fa03a82dfc423db671f3633efa6ab97ff4339b1 0.417105520576 93878 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": 50639, "vin": [ { "gen": { "height": 50629 } } ], "vout": [ { "amount": 417105520576, "target": { "key": "aec04e0c7126478273e05ba76fa03a82dfc423db671f3633efa6ab97ff4339b1" } } ], "extra": [ 1, 220, 109, 2, 81, 114, 64, 84, 236, 142, 238, 132, 72, 144, 242, 160, 155, 88, 179, 74, 63, 59, 138, 68, 77, 167, 15, 141, 242, 172, 151, 183, 17, 2, 17, 0, 0, 0, 77, 57, 26, 141, 14, 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: