Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6691522815e247c537de5898df8eaa245032c0266f52db1137d2d69dfad4585

Tx prefix hash: 3580cefd1936f3a894c5de78f0ee5355ddcec04f4c7a302a91bdee7fb3600bf1
Tx public key: eee785451d0e0c9dfb099c18a2ead15664a2230fd6c6c46a8ab222d284764781
Timestamp: 1728617151 Timestamp [UCT]: 2024-10-11 03:25:51 Age [y:d:h:m:s]: 00:187:18:45:20
Block: 1128994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134004 RingCT/type: yes/0
Extra: 01eee785451d0e0c9dfb099c18a2ead15664a2230fd6c6c46a8ab222d28476478102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c7cfef1e622609979d0d12f761c81e9692568e625cec57caed2cfb0510be424 0.600000000000 1611817 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": 1129004, "vin": [ { "gen": { "height": 1128994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c7cfef1e622609979d0d12f761c81e9692568e625cec57caed2cfb0510be424" } } ], "extra": [ 1, 238, 231, 133, 69, 29, 14, 12, 157, 251, 9, 156, 24, 162, 234, 209, 86, 100, 162, 35, 15, 214, 198, 196, 106, 138, 178, 34, 210, 132, 118, 71, 129, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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