Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5cfb7b025209b99d11b2fba6d8acd46ec78d0dafee2128452c115ab3d662687

Tx prefix hash: e35cb1f1b97268705c8d3d89f5f3594269d69985c477aca21c4fecc887eea000
Tx public key: 403e7a76ca355e5b98467330b42f2170b59e1a33ce5ae5e8486110608758d91d
Timestamp: 1716678415 Timestamp [UCT]: 2024-05-25 23:06:55 Age [y:d:h:m:s]: 01:018:00:29:37
Block: 1030022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273759 RingCT/type: yes/0
Extra: 01403e7a76ca355e5b98467330b42f2170b59e1a33ce5ae5e8486110608758d91d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15fcd18e68e76f618cb3f6155786de6b703a5e327122f3a7fa2e3c5f79398031 0.600000000000 1498267 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": 1030032, "vin": [ { "gen": { "height": 1030022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15fcd18e68e76f618cb3f6155786de6b703a5e327122f3a7fa2e3c5f79398031" } } ], "extra": [ 1, 64, 62, 122, 118, 202, 53, 94, 91, 152, 70, 115, 48, 180, 47, 33, 112, 181, 158, 26, 51, 206, 90, 229, 232, 72, 97, 16, 96, 135, 88, 217, 29, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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