Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 224a9017147b760dfb99b825daeb647156ea9af8f7cda9a96f662e279c53bff5

Tx prefix hash: 223e52b0a5b06143443b66247e26b98d911a19ba26fb30ffabb360f61bb1e4ee
Tx public key: 2cd013df645d3ab8a6a3141a602c5a6ca15518a9d53dd4e06f77f5fa47c4ac8a
Timestamp: 1694982845 Timestamp [UCT]: 2023-09-17 20:34:05 Age [y:d:h:m:s]: 01:202:18:41:53
Block: 850337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406013 RingCT/type: yes/0
Extra: 012cd013df645d3ab8a6a3141a602c5a6ca15518a9d53dd4e06f77f5fa47c4ac8a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.934287597000 dcy

stealth address amount amount idx
00: 462facdb97dfa1db25fbdc01bba1c27000580336ac742b250a229cffc19e754e 0.934287597000 1304051 of 0

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": 850347, "vin": [ { "gen": { "height": 850337 } } ], "vout": [ { "amount": 934287597, "target": { "key": "462facdb97dfa1db25fbdc01bba1c27000580336ac742b250a229cffc19e754e" } } ], "extra": [ 1, 44, 208, 19, 223, 100, 93, 58, 184, 166, 163, 20, 26, 96, 44, 90, 108, 161, 85, 24, 169, 213, 61, 212, 224, 111, 119, 245, 250, 71, 196, 172, 138, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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