Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c12dde9962aeaf40434fb020554420f8fe1fea84c0812c15e68dfb52f7c24543

Tx prefix hash: 29f94f945643843b552106648a43ea1fc67c0d3bc1d65dee1ba3e1f4669a26c8
Tx public key: 973fdc09cb92e2d0c877cb3796c140cd16893b8943e8dc33cc61c3909806b5b6
Timestamp: 1736787074 Timestamp [UCT]: 2025-01-13 16:51:14 Age [y:d:h:m:s]: 00:062:00:25:04
Block: 1196592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44106 RingCT/type: yes/0
Extra: 01973fdc09cb92e2d0c877cb3796c140cd16893b8943e8dc33cc61c3909806b5b60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b07dfba15991fb6cfee85f4bad67ae6bdfbe7c95bb274bd5b81aa87973e704f 0.600000000000 1683191 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": 1196602, "vin": [ { "gen": { "height": 1196592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b07dfba15991fb6cfee85f4bad67ae6bdfbe7c95bb274bd5b81aa87973e704f" } } ], "extra": [ 1, 151, 63, 220, 9, 203, 146, 226, 208, 200, 119, 203, 55, 150, 193, 64, 205, 22, 137, 59, 137, 67, 232, 220, 51, 204, 97, 195, 144, 152, 6, 181, 182, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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