Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aba31574cac17ea6460ed5dd29a0e2865dfa4cf1b7efc10f94f992ae93827020

Tx prefix hash: 58213621a0e8b2b47df4fd364823e9003c96d7f5c3c95b9399183bc330ba38fd
Tx public key: d8f2c4e3d956e918aaddfb9a3c79e89a5cd50321067fedcb32b0fc255bd23c0f
Timestamp: 1677846249 Timestamp [UCT]: 2023-03-03 12:24:09 Age [y:d:h:m:s]: 01:359:11:15:28
Block: 708966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517582 RingCT/type: yes/0
Extra: 01d8f2c4e3d956e918aaddfb9a3c79e89a5cd50321067fedcb32b0fc255bd23c0f0211000000035029cbac000000000000000000

1 output(s) for total of 2.747269321000 dcy

stealth address amount amount idx
00: d1e78003efca2ef7641f35aaffd9157dc056735d5a6b81330a1ab397d68b3382 2.747269321000 1152895 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 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": 708976, "vin": [ { "gen": { "height": 708966 } } ], "vout": [ { "amount": 2747269321, "target": { "key": "d1e78003efca2ef7641f35aaffd9157dc056735d5a6b81330a1ab397d68b3382" } } ], "extra": [ 1, 216, 242, 196, 227, 217, 86, 233, 24, 170, 221, 251, 154, 60, 121, 232, 154, 92, 213, 3, 33, 6, 127, 237, 203, 50, 176, 252, 37, 91, 210, 60, 15, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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