Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc50028a13c675f5ebefe61eb3f386e5a4997047246b01d33d0d0793875323b

Tx prefix hash: 70628a3db3cea9a6321d670a257d3fd34edaa592dc5c4b323d70bdc8c0b44a58
Tx public key: 686b9d71f4e25d5e5a60e4f084764ca08e83f9203ff6cdcad4aedd538b432dd7
Timestamp: 1711707385 Timestamp [UCT]: 2024-03-29 10:16:25 Age [y:d:h:m:s]: 01:018:11:57:23
Block: 988819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274179 RingCT/type: yes/0
Extra: 01686b9d71f4e25d5e5a60e4f084764ca08e83f9203ff6cdcad4aedd538b432dd70211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc9dea33cc3b62e66ddcdf72b036641f9d827415f6a40c018e7bdf7dd5f780bb 0.600000000000 1449104 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": 988829, "vin": [ { "gen": { "height": 988819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc9dea33cc3b62e66ddcdf72b036641f9d827415f6a40c018e7bdf7dd5f780bb" } } ], "extra": [ 1, 104, 107, 157, 113, 244, 226, 93, 94, 90, 96, 228, 240, 132, 118, 76, 160, 142, 131, 249, 32, 63, 246, 205, 202, 212, 174, 221, 83, 139, 67, 45, 215, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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