Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aebbc6f2e75c01f83f397e403989eb6c80078b6bf8a869fd6eb2608612b9c8f7

Tx prefix hash: eeb64e911cf59fdcdde7d86cf40479b0e80805f29a833072df63d3936580c5e9
Tx public key: 8c17cd607eb9e0e844e70ebf902c376bd2345bcae81c1b4b6e78311e1013785c
Timestamp: 1716348799 Timestamp [UCT]: 2024-05-22 03:33:19 Age [y:d:h:m:s]: 00:281:15:11:21
Block: 1027290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201257 RingCT/type: yes/0
Extra: 018c17cd607eb9e0e844e70ebf902c376bd2345bcae81c1b4b6e78311e1013785c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87a82fba67fc5a9ab0f09d432e5af009d6584e6840773d3244f3205b38f2a6f4 0.600000000000 1494829 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": 1027300, "vin": [ { "gen": { "height": 1027290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87a82fba67fc5a9ab0f09d432e5af009d6584e6840773d3244f3205b38f2a6f4" } } ], "extra": [ 1, 140, 23, 205, 96, 126, 185, 224, 232, 68, 231, 14, 191, 144, 44, 55, 107, 210, 52, 91, 202, 232, 28, 27, 75, 110, 120, 49, 30, 16, 19, 120, 92, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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