Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 931529124b210c48c18cc5954b417fdb60d5d32e4a0c16b14dcd452b75dc708b

Tx prefix hash: 0bf95cc51a1d1a372460177447a5ce20f63d3172824d6e3efaae22054b05d250
Tx public key: 991219084e92ffc5f5d5487f2b495656a6f556b25bf529deb411fcd6aab5d504
Timestamp: 1710627249 Timestamp [UCT]: 2024-03-16 22:14:09 Age [y:d:h:m:s]: 00:343:08:33:42
Block: 979866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245453 RingCT/type: yes/0
Extra: 01991219084e92ffc5f5d5487f2b495656a6f556b25bf529deb411fcd6aab5d5040211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94bee4d26f9b1b1bcea3ba1ab6190cad42f4d4e4429c10c64db4e06fdc378ae9 0.600000000000 1439921 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": 979876, "vin": [ { "gen": { "height": 979866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94bee4d26f9b1b1bcea3ba1ab6190cad42f4d4e4429c10c64db4e06fdc378ae9" } } ], "extra": [ 1, 153, 18, 25, 8, 78, 146, 255, 197, 245, 213, 72, 127, 43, 73, 86, 86, 166, 245, 86, 178, 91, 245, 41, 222, 180, 17, 252, 214, 170, 181, 213, 4, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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