Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 466ee37bf3696686b4bbf924cddab1cbcaab9b8226d32bb033d89e9cd6f55a38

Tx prefix hash: d1a15dd46a1048dcf0333a4c136e222747455891395f6079e679f43df5f0fc5d
Tx public key: ff3b31e82518274cb971c3d9d7955709f38153d79f6098dc8429cdb99082dba3
Timestamp: 1730138982 Timestamp [UCT]: 2024-10-28 18:09:42 Age [y:d:h:m:s]: 00:183:13:14:53
Block: 1141545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131034 RingCT/type: yes/0
Extra: 01ff3b31e82518274cb971c3d9d7955709f38153d79f6098dc8429cdb99082dba3021100000011007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1c0c7164e781755e401c046d8b594f21f4f402a671604c8d7e503e2bd691465 0.600000000000 1625352 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": 1141555, "vin": [ { "gen": { "height": 1141545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1c0c7164e781755e401c046d8b594f21f4f402a671604c8d7e503e2bd691465" } } ], "extra": [ 1, 255, 59, 49, 232, 37, 24, 39, 76, 185, 113, 195, 217, 215, 149, 87, 9, 243, 129, 83, 215, 159, 96, 152, 220, 132, 41, 205, 185, 144, 130, 219, 163, 2, 17, 0, 0, 0, 17, 0, 127, 151, 138, 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