Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f58a2194363334626621c34a87881072b22e57950bf979d3c264a05dafae1631

Tx prefix hash: 9f5597ad97e4177b918f34d5ae8f4ce52a73085b20015b7a2f5664af1fb7f2f4
Tx public key: 9dc8111a7b0fba28116ddd831d5bf4ec524b802bdc0e3ca4fe8d3b19e5ba2d40
Timestamp: 1734067220 Timestamp [UCT]: 2024-12-13 05:20:20 Age [y:d:h:m:s]: 00:102:06:18:45
Block: 1174093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72849 RingCT/type: yes/0
Extra: 019dc8111a7b0fba28116ddd831d5bf4ec524b802bdc0e3ca4fe8d3b19e5ba2d40021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e6a014e5fd1e04abeccc95e85ef0cb07bf85cd09b1c6d7a456969caf2f79dc9 0.600000000000 1660200 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": 1174103, "vin": [ { "gen": { "height": 1174093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e6a014e5fd1e04abeccc95e85ef0cb07bf85cd09b1c6d7a456969caf2f79dc9" } } ], "extra": [ 1, 157, 200, 17, 26, 123, 15, 186, 40, 17, 109, 221, 131, 29, 91, 244, 236, 82, 75, 128, 43, 220, 14, 60, 164, 254, 141, 59, 25, 229, 186, 45, 64, 2, 17, 0, 0, 0, 2, 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