Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36d695fc9815a1b973300ccaa2218a98593928d055331041277fb530796a7fe2

Tx prefix hash: 184d225735f3b50abcc6d06102d9e7c78e998b7a3a3f23bbdda7773da759c371
Tx public key: b0f8e8c987d38d33224a28d238f3d456f1779224d3c078a6df0c6e6e0a756a55
Timestamp: 1729567553 Timestamp [UCT]: 2024-10-22 03:25:53 Age [y:d:h:m:s]: 00:171:05:23:35
Block: 1136829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122195 RingCT/type: yes/0
Extra: 01b0f8e8c987d38d33224a28d238f3d456f1779224d3c078a6df0c6e6e0a756a550211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baf8568cc11b2323e598dd9e3802dddbdcd5f104489b3579ee2eba2bdbd6955d 0.600000000000 1620210 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": 1136839, "vin": [ { "gen": { "height": 1136829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baf8568cc11b2323e598dd9e3802dddbdcd5f104489b3579ee2eba2bdbd6955d" } } ], "extra": [ 1, 176, 248, 232, 201, 135, 211, 141, 51, 34, 74, 40, 210, 56, 243, 212, 86, 241, 119, 146, 36, 211, 192, 120, 166, 223, 12, 110, 110, 10, 117, 106, 85, 2, 17, 0, 0, 0, 5, 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