Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866ca807ea50fc6f1fddce34f78d494913fab6e3a637fad13fa485a9b6b48cb8

Tx prefix hash: ff6ff0b3fa22557aac05a1e9174cf929264b95fa96ed49ab718e411fdef5ba8f
Tx public key: c3754b16480d4fe8df9d8526a33d3f1dee422a1a929aba3fd18f05b599648e6a
Timestamp: 1710473238 Timestamp [UCT]: 2024-03-15 03:27:18 Age [y:d:h:m:s]: 01:234:23:16:50
Block: 978595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426610 RingCT/type: yes/0
Extra: 01c3754b16480d4fe8df9d8526a33d3f1dee422a1a929aba3fd18f05b599648e6a02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ef14af47cc1b0c06170dd47b5f46bdee6758ee5bd68e3a274757c02707e7c95 0.600000000000 1438622 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": 978605, "vin": [ { "gen": { "height": 978595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ef14af47cc1b0c06170dd47b5f46bdee6758ee5bd68e3a274757c02707e7c95" } } ], "extra": [ 1, 195, 117, 75, 22, 72, 13, 79, 232, 223, 157, 133, 38, 163, 61, 63, 29, 238, 66, 42, 26, 146, 154, 186, 63, 209, 143, 5, 181, 153, 100, 142, 106, 2, 17, 0, 0, 0, 8, 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