Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbea4a8013024097f1506fdb51750e118b4568dbfd0144d753ebedb9f65d64d3

Tx prefix hash: 5b8b4fb16bef2e61803e5241dc061960b3fb02fbd51d46d3a6206babc0eb31e2
Tx public key: c5b27535e785216cbdf38ce55375ca88012dd4fe27c5c458eb3e3d83dbbae963
Timestamp: 1731712288 Timestamp [UCT]: 2024-11-15 23:11:28 Age [y:d:h:m:s]: 00:008:03:43:52
Block: 1154572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5833 RingCT/type: yes/0
Extra: 01c5b27535e785216cbdf38ce55375ca88012dd4fe27c5c458eb3e3d83dbbae963021100000015a417ef1c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37b09011cb3cf13362976c4b1d083484ec9eb5ab026d2c4c347cc016ac5fcf97 0.600000000000 1640185 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": 1154582, "vin": [ { "gen": { "height": 1154572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37b09011cb3cf13362976c4b1d083484ec9eb5ab026d2c4c347cc016ac5fcf97" } } ], "extra": [ 1, 197, 178, 117, 53, 231, 133, 33, 108, 189, 243, 140, 229, 83, 117, 202, 136, 1, 45, 212, 254, 39, 197, 196, 88, 235, 62, 61, 131, 219, 186, 233, 99, 2, 17, 0, 0, 0, 21, 164, 23, 239, 28, 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