Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 354d56471a8df2689169e86ba5f693ea2ef1823f03f9da982504d2d7cfe3e471

Tx prefix hash: e7674d9d4057dc38f0f286b38e2ec11249d8f0963af411062002bd6d6d0f8532
Tx public key: 3a8087c85bd31256331608e3d0aabf3d73a9104d59c84f3af02587b4cdadaad4
Timestamp: 1726767839 Timestamp [UCT]: 2024-09-19 17:43:59 Age [y:d:h:m:s]: 00:156:17:10:52
Block: 1113661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111786 RingCT/type: yes/0
Extra: 013a8087c85bd31256331608e3d0aabf3d73a9104d59c84f3af02587b4cdadaad4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 694fb53caa9fdcf8a413a75bd70f9e094b513de948bbda9ad5e322939b4dc2ae 0.600000000000 1593412 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": 1113671, "vin": [ { "gen": { "height": 1113661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "694fb53caa9fdcf8a413a75bd70f9e094b513de948bbda9ad5e322939b4dc2ae" } } ], "extra": [ 1, 58, 128, 135, 200, 91, 211, 18, 86, 51, 22, 8, 227, 208, 170, 191, 61, 115, 169, 16, 77, 89, 200, 79, 58, 240, 37, 135, 180, 205, 173, 170, 212, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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