Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c58c37cfac01084df099be7fa65b26bb10778daa45eec738b0f4722de06e31fd

Tx prefix hash: 434e1db605b1060e453e7904625f58d3277981e777631043ecbb97ccb64162e7
Tx public key: 908914889cbe4ddc44f4796ff323c0c98a5c4ecf9941e0b93b2d024acf4fcc6b
Timestamp: 1734330772 Timestamp [UCT]: 2024-12-16 06:32:52 Age [y:d:h:m:s]: 00:094:11:07:57
Block: 1176274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67302 RingCT/type: yes/0
Extra: 01908914889cbe4ddc44f4796ff323c0c98a5c4ecf9941e0b93b2d024acf4fcc6b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a048c9e3e8c6f58abcf218ca8f5294adeed30cd0a41afd75d43c3b26a7250f7c 0.600000000000 1662605 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": 1176284, "vin": [ { "gen": { "height": 1176274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a048c9e3e8c6f58abcf218ca8f5294adeed30cd0a41afd75d43c3b26a7250f7c" } } ], "extra": [ 1, 144, 137, 20, 136, 156, 190, 77, 220, 68, 244, 121, 111, 243, 35, 192, 201, 138, 92, 78, 207, 153, 65, 224, 185, 59, 45, 2, 74, 207, 79, 204, 107, 2, 17, 0, 0, 0, 6, 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