Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61eff0be9d5381a3edeb2542286b39cb4345171c1e370b2a331996075c2ae27a

Tx prefix hash: 762b38931dc3f54f35df72cde1963ffc90e922b4fdf2055c182b774e1d57506f
Tx public key: 4149818f8e9c1270220b657909c5a8bafd128326445136a5fe5f062c0e2a88ac
Timestamp: 1721982049 Timestamp [UCT]: 2024-07-26 08:20:49 Age [y:d:h:m:s]: 00:234:22:11:30
Block: 1073985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167807 RingCT/type: yes/0
Extra: 014149818f8e9c1270220b657909c5a8bafd128326445136a5fe5f062c0e2a88ac02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fb477242f54bdda8968f1b46e7d22382a40439f222178bc2445f90b78524b41 0.600000000000 1546494 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": 1073995, "vin": [ { "gen": { "height": 1073985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fb477242f54bdda8968f1b46e7d22382a40439f222178bc2445f90b78524b41" } } ], "extra": [ 1, 65, 73, 129, 143, 142, 156, 18, 112, 34, 11, 101, 121, 9, 197, 168, 186, 253, 18, 131, 38, 68, 81, 54, 165, 254, 95, 6, 44, 14, 42, 136, 172, 2, 17, 0, 0, 0, 11, 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