Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ff516a9b11ea946f3a677a3640ecc1c8741c9bf2ec5d75115d878a29b7160d2

Tx prefix hash: 2827051a1be4d4dcee0d49c8ee1a18638c61c75f72c0f9acb869ad5eee69db81
Tx public key: 8f1be46d73298f017a9c4e0be4907597776132c4fe431dfcdf24e9f92c63ad9f
Timestamp: 1704952186 Timestamp [UCT]: 2024-01-11 05:49:46 Age [y:d:h:m:s]: 02:021:09:18:18
Block: 932779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534920 RingCT/type: yes/0
Extra: 018f1be46d73298f017a9c4e0be4907597776132c4fe431dfcdf24e9f92c63ad9f0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eb43ef3c61c9ec73d0d2cb954f0a42e849422a2a7c67f508e59b41b8b74c427 0.600000000000 1390719 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": 932789, "vin": [ { "gen": { "height": 932779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eb43ef3c61c9ec73d0d2cb954f0a42e849422a2a7c67f508e59b41b8b74c427" } } ], "extra": [ 1, 143, 27, 228, 109, 115, 41, 143, 1, 122, 156, 78, 11, 228, 144, 117, 151, 119, 97, 50, 196, 254, 67, 29, 252, 223, 36, 233, 249, 44, 99, 173, 159, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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