Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 212de28f487fa9bf84f5ce3f42ffc594b548d95a772467fec4dabebe464b5b54

Tx prefix hash: a0163bf8ddc488e26ac72b462765a0085c45a9a13bce27a7e7ba64eb7931c9c4
Tx public key: feccf81a4985bf0c6d0261e15359e5df1b857c7c9ca72381e189247b2b6bd8d4
Timestamp: 1733808390 Timestamp [UCT]: 2024-12-10 05:26:30 Age [y:d:h:m:s]: 00:099:04:37:40
Block: 1171938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70693 RingCT/type: yes/0
Extra: 01feccf81a4985bf0c6d0261e15359e5df1b857c7c9ca72381e189247b2b6bd8d40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b3d939e88ad3718a1f8c3d05a2c802ecb0572d72ddee84daa8cfefe583c2174 0.600000000000 1657763 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": 1171948, "vin": [ { "gen": { "height": 1171938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b3d939e88ad3718a1f8c3d05a2c802ecb0572d72ddee84daa8cfefe583c2174" } } ], "extra": [ 1, 254, 204, 248, 26, 73, 133, 191, 12, 109, 2, 97, 225, 83, 89, 229, 223, 27, 133, 124, 124, 156, 167, 35, 129, 225, 137, 36, 123, 43, 107, 216, 212, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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