Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce63e012e0866c643b0459118fccdf7e84dc39a3c0f730030d904f3fd606f794

Tx prefix hash: 3937ed1141ca95a432501b169ee0b126d870a547e6acf06d0905022c757b3ad7
Tx public key: 06f7176d0845f59996079025173167d12d526f36f55f84d926dbef417dc0b30e
Timestamp: 1694237295 Timestamp [UCT]: 2023-09-09 05:28:15 Age [y:d:h:m:s]: 01:211:20:06:13
Block: 844144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412498 RingCT/type: yes/0
Extra: 0106f7176d0845f59996079025173167d12d526f36f55f84d926dbef417dc0b30e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.979491276000 dcy

stealth address amount amount idx
00: 49adb44a8a9822689d3ec528d1f2dca59b332751adb7ed958ebb20e75193a6f9 0.979491276000 1297434 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": 844154, "vin": [ { "gen": { "height": 844144 } } ], "vout": [ { "amount": 979491276, "target": { "key": "49adb44a8a9822689d3ec528d1f2dca59b332751adb7ed958ebb20e75193a6f9" } } ], "extra": [ 1, 6, 247, 23, 109, 8, 69, 245, 153, 150, 7, 144, 37, 23, 49, 103, 209, 45, 82, 111, 54, 245, 95, 132, 217, 38, 219, 239, 65, 125, 192, 179, 14, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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