Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c7fe753a77f40ffa2161d5bd0f863ca35362be7124272fd763cd5dad6411673

Tx prefix hash: 43155fb94648e8a9b03d5e5fa3bcec0fdd1d8f073988434c955d1462d1742f56
Tx public key: ee19d5b09d3e96c7e876541b405b3f51ade2621db37e208ce16c93570fc61d52
Timestamp: 1689598070 Timestamp [UCT]: 2023-07-17 12:47:50 Age [y:d:h:m:s]: 01:257:23:18:57
Block: 805772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445483 RingCT/type: yes/0
Extra: 01ee19d5b09d3e96c7e876541b405b3f51ade2621db37e208ce16c93570fc61d5202110000000833af99f4000000000000000000

1 output(s) for total of 1.312632018000 dcy

stealth address amount amount idx
00: 37e47a9faf7ca8fdfb60cb370a8c3a841775b4544582f3102cd15f05b1df4da1 1.312632018000 1257047 of 0

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": 805782, "vin": [ { "gen": { "height": 805772 } } ], "vout": [ { "amount": 1312632018, "target": { "key": "37e47a9faf7ca8fdfb60cb370a8c3a841775b4544582f3102cd15f05b1df4da1" } } ], "extra": [ 1, 238, 25, 213, 176, 157, 62, 150, 199, 232, 118, 84, 27, 64, 91, 63, 81, 173, 226, 98, 29, 179, 126, 32, 140, 225, 108, 147, 87, 15, 198, 29, 82, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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