Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 428e41851fa8d279cc9a40b183a66228a918f0eec06ab6e67b0e9e9f07b7a403

Tx prefix hash: db07fe89811034b8be27a50a4a134e64a4b8d8101ffa3a8126ce397bf944a6b1
Tx public key: 78314fb24d4004ce5ebf1ff0fdddef191f93a86b091b5667694e4d25fd6ff956
Timestamp: 1736357247 Timestamp [UCT]: 2025-01-08 17:27:27 Age [y:d:h:m:s]: 00:162:04:55:24
Block: 1193027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115616 RingCT/type: yes/0
Extra: 0178314fb24d4004ce5ebf1ff0fdddef191f93a86b091b5667694e4d25fd6ff956021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a54d2ecd8ea0b602b1a3fb9b5426c43bdd61c4f582e8466a85aeb5e3480e531 0.600000000000 1679584 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": 1193037, "vin": [ { "gen": { "height": 1193027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a54d2ecd8ea0b602b1a3fb9b5426c43bdd61c4f582e8466a85aeb5e3480e531" } } ], "extra": [ 1, 120, 49, 79, 178, 77, 64, 4, 206, 94, 191, 31, 240, 253, 221, 239, 25, 31, 147, 168, 107, 9, 27, 86, 103, 105, 78, 77, 37, 253, 111, 249, 86, 2, 17, 0, 0, 0, 4, 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