Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baef03e08ff9517696ccf367e798ee67d81623e859d108e352db9b8b2d37e52b

Tx prefix hash: 040be330525a41c1735a49126a7acc1ab7608bb131367a0053822dc049d7bfd7
Tx public key: ad783e7c309968e7ed19f40f22345aea1c373222427f3abf4a34d33027fdb37d
Timestamp: 1696361584 Timestamp [UCT]: 2023-10-03 19:33:04 Age [y:d:h:m:s]: 01:186:06:11:25
Block: 861780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394155 RingCT/type: yes/0
Extra: 01ad783e7c309968e7ed19f40f22345aea1c373222427f3abf4a34d33027fdb37d021100000006faf35c9c000000000000000000

1 output(s) for total of 0.856180155000 dcy

stealth address amount amount idx
00: e47c56942f7befbe00e56a8979a1677fd58842fe79415dc2f09caf9e4fe0e61b 0.856180155000 1316150 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": 861790, "vin": [ { "gen": { "height": 861780 } } ], "vout": [ { "amount": 856180155, "target": { "key": "e47c56942f7befbe00e56a8979a1677fd58842fe79415dc2f09caf9e4fe0e61b" } } ], "extra": [ 1, 173, 120, 62, 124, 48, 153, 104, 231, 237, 25, 244, 15, 34, 52, 90, 234, 28, 55, 50, 34, 66, 127, 58, 191, 74, 52, 211, 48, 39, 253, 179, 125, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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