Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6ca49e964ca2d3724eea092fc3dad09aa69bda436411babf0a2c4cd1a99ea16

Tx prefix hash: 776a689536f58c2e6e55f91799ce0b35bcaccbb2eb647f1596d81660f2daaa73
Tx public key: 3c4efba8bbca83a2a2f9a64d040d45b3a4464c024985273732896c367f650681
Timestamp: 1715522168 Timestamp [UCT]: 2024-05-12 13:56:08 Age [y:d:h:m:s]: 00:288:15:42:06
Block: 1020464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206259 RingCT/type: yes/0
Extra: 013c4efba8bbca83a2a2f9a64d040d45b3a4464c024985273732896c367f650681021100000004c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b942b86f6abb931e1f946ad79c9f972bea2330f8ce7b2f26412e184790729903 0.600000000000 1484537 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 dinasty-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": 1020474, "vin": [ { "gen": { "height": 1020464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b942b86f6abb931e1f946ad79c9f972bea2330f8ce7b2f26412e184790729903" } } ], "extra": [ 1, 60, 78, 251, 168, 187, 202, 131, 162, 162, 249, 166, 77, 4, 13, 69, 179, 164, 70, 76, 2, 73, 133, 39, 55, 50, 137, 108, 54, 127, 101, 6, 129, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8