Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c11ffe0c1619f0cec55dcf2251fc8da78798e792cf38b46831f3bdb253581b0e

Tx prefix hash: 29caef9fa12fa52c03d6bb6ab36cd38e9d9b9f835e204379c5ad9b09cd4f4169
Tx public key: 40ce28c3dfe8ff00d12db980dbe458ab1f250405ebce11e8a5f73ca92f1e58bc
Timestamp: 1631744249 Timestamp [UCT]: 2021-09-15 22:17:29 Age [y:d:h:m:s]: 04:046:09:25:52
Block: 334569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067218 RingCT/type: yes/0
Extra: 0140ce28c3dfe8ff00d12db980dbe458ab1f250405ebce11e8a5f73ca92f1e58bc02110000012836fe6557000000000000000000

1 output(s) for total of 47.808662026000 dcy

stealth address amount amount idx
00: 7f5342df60ec64fb727fc884ee807e8c1b07eb0536b90eadd6bde715a982a9fb 47.808662026000 690030 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": 334579, "vin": [ { "gen": { "height": 334569 } } ], "vout": [ { "amount": 47808662026, "target": { "key": "7f5342df60ec64fb727fc884ee807e8c1b07eb0536b90eadd6bde715a982a9fb" } } ], "extra": [ 1, 64, 206, 40, 195, 223, 232, 255, 0, 209, 45, 185, 128, 219, 228, 88, 171, 31, 37, 4, 5, 235, 206, 17, 232, 165, 247, 60, 169, 47, 30, 88, 188, 2, 17, 0, 0, 1, 40, 54, 254, 101, 87, 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