Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b72e49d816c805ae085798da9a4686f1446d51f3e8d0ae3c3f89e0ebd702380

Tx prefix hash: 87a8262194f3344cedd45ee3a4cb64e6208a0f4e20459ec6affabc66858a8330
Tx public key: ba8177c970ccb3f5af4e0e183100ad7818be22e3d3c45ee589bf53f087a6431d
Timestamp: 1728208498 Timestamp [UCT]: 2024-10-06 09:54:58 Age [y:d:h:m:s]: 00:048:21:58:08
Block: 1125616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34933 RingCT/type: yes/0
Extra: 01ba8177c970ccb3f5af4e0e183100ad7818be22e3d3c45ee589bf53f087a6431d02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40766b96a65ccc0c3d85632750003211f8b51953558a78e89712da6b5b9ef02f 0.600000000000 1608367 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": 1125626, "vin": [ { "gen": { "height": 1125616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40766b96a65ccc0c3d85632750003211f8b51953558a78e89712da6b5b9ef02f" } } ], "extra": [ 1, 186, 129, 119, 201, 112, 204, 179, 245, 175, 78, 14, 24, 49, 0, 173, 120, 24, 190, 34, 227, 211, 196, 94, 229, 137, 191, 83, 240, 135, 166, 67, 29, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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