Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d686cfc2c8e7c6b2ade6946591be1a6379ddd33a1b3dc99e1655382937372cf

Tx prefix hash: 3ae2dddb1823d1b50c2690c2a3e4e7d1316989e9f7a9a843e5faf63e4183fe29
Tx public key: fae7f8b4da37cd9b68d428017c56309bddd5d1a93384a59e2aa6d60f044962f4
Timestamp: 1703322594 Timestamp [UCT]: 2023-12-23 09:09:54 Age [y:d:h:m:s]: 01:348:18:05:49
Block: 919289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508122 RingCT/type: yes/0
Extra: 01fae7f8b4da37cd9b68d428017c56309bddd5d1a93384a59e2aa6d60f044962f40211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6e94c5152ef9df0c3254a1c05ed3d23e0b5b04eae0fb85b8235f347ffaa45e4 0.600000000000 1376955 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": 919299, "vin": [ { "gen": { "height": 919289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6e94c5152ef9df0c3254a1c05ed3d23e0b5b04eae0fb85b8235f347ffaa45e4" } } ], "extra": [ 1, 250, 231, 248, 180, 218, 55, 205, 155, 104, 212, 40, 1, 124, 86, 48, 155, 221, 213, 209, 169, 51, 132, 165, 158, 42, 166, 214, 15, 4, 73, 98, 244, 2, 17, 0, 0, 0, 6, 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