Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e2fefabf1c30b78e743af345efaf66f7e518170ff7d98c3db3ed917308f7e4

Tx prefix hash: af2f7b66bb87b509bf611bb8541b86bc0138d7fe08ed46f061d07ceb1edab586
Tx public key: 5e51f3f0c50079d10c8a374e5c0b6bdfa21f96f6912da50ab457ee426fac0d86
Timestamp: 1712371803 Timestamp [UCT]: 2024-04-06 02:50:03 Age [y:d:h:m:s]: 01:078:17:01:08
Block: 994280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317040 RingCT/type: yes/0
Extra: 015e51f3f0c50079d10c8a374e5c0b6bdfa21f96f6912da50ab457ee426fac0d860211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfd4e15204a0c75a6900d3f2a3b3b99433584dfeb3f02bf48ecfe86d1619480f 0.600000000000 1454682 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": 994290, "vin": [ { "gen": { "height": 994280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfd4e15204a0c75a6900d3f2a3b3b99433584dfeb3f02bf48ecfe86d1619480f" } } ], "extra": [ 1, 94, 81, 243, 240, 197, 0, 121, 209, 12, 138, 55, 78, 92, 11, 107, 223, 162, 31, 150, 246, 145, 45, 165, 10, 180, 87, 238, 66, 111, 172, 13, 134, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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