Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24f7050ef42cce5d5fa90fc1060a3bc56ac452ee365b83c1d9730741b665c06

Tx prefix hash: 596f6e4dde0f03d22b9c6e376da81bdf485de02995de0a8e92c410949ab45efe
Tx public key: 340141f557e878dbd37b2f89e42fc4389b8099a9c9a9b0a4a9443d64007c4b7e
Timestamp: 1722966175 Timestamp [UCT]: 2024-08-06 17:42:55 Age [y:d:h:m:s]: 01:095:03:55:41
Block: 1082144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326491 RingCT/type: yes/0
Extra: 01340141f557e878dbd37b2f89e42fc4389b8099a9c9a9b0a4a9443d64007c4b7e021100000016e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a1c329a14e073bb7e3271a93ade4a34099cba671d1246a380c0a69c611c6756 0.600000000000 1555967 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": 1082154, "vin": [ { "gen": { "height": 1082144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a1c329a14e073bb7e3271a93ade4a34099cba671d1246a380c0a69c611c6756" } } ], "extra": [ 1, 52, 1, 65, 245, 87, 232, 120, 219, 211, 123, 47, 137, 228, 47, 196, 56, 155, 128, 153, 169, 201, 169, 176, 164, 169, 68, 61, 100, 0, 124, 75, 126, 2, 17, 0, 0, 0, 22, 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