Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e699cedca6e690c5a13f16eacc83f83f3f4f41e25f2fd5b04de7bd02fe61710

Tx prefix hash: a167c7935ada97e144ffd25e12a19b57ae107408acbc30dcee314059f09935bd
Tx public key: 78f0459e88a3250218b3d2a8b5dc8d825a698beb1877fb93fa9956f31297031f
Timestamp: 1703965643 Timestamp [UCT]: 2023-12-30 19:47:23 Age [y:d:h:m:s]: 02:030:14:38:55
Block: 924615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541513 RingCT/type: yes/0
Extra: 0178f0459e88a3250218b3d2a8b5dc8d825a698beb1877fb93fa9956f31297031f021100000004ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9b5389229b535f52c1928bc6ef4215d747645f26e04d871c5cea10d661ef514 0.600000000000 1382371 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": 924625, "vin": [ { "gen": { "height": 924615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9b5389229b535f52c1928bc6ef4215d747645f26e04d871c5cea10d661ef514" } } ], "extra": [ 1, 120, 240, 69, 158, 136, 163, 37, 2, 24, 179, 210, 168, 181, 220, 141, 130, 90, 105, 139, 235, 24, 119, 251, 147, 250, 153, 86, 243, 18, 151, 3, 31, 2, 17, 0, 0, 0, 4, 172, 50, 141, 17, 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