Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01481593b2ec90ce315fb3e31d37a2b7dec5d8ebd4238a04b82ee27d4ab2062e

Tx prefix hash: 4efb19c996ece98afccfe618f4339b789792db39090440ce6868ed8a5e91e9ea
Tx public key: 93f0392397b13ac3257f8a6d05e08d9522f9dc138b42acaf4e90533e2a3eecbc
Timestamp: 1705206491 Timestamp [UCT]: 2024-01-14 04:28:11 Age [y:d:h:m:s]: 01:300:11:27:33
Block: 934885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473581 RingCT/type: yes/0
Extra: 0193f0392397b13ac3257f8a6d05e08d9522f9dc138b42acaf4e90533e2a3eecbc0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbe2b8f9d98f422cf4790f33c4b5ea04702d33423ef866189afc8492be38fc53 0.600000000000 1392901 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": 934895, "vin": [ { "gen": { "height": 934885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbe2b8f9d98f422cf4790f33c4b5ea04702d33423ef866189afc8492be38fc53" } } ], "extra": [ 1, 147, 240, 57, 35, 151, 177, 58, 195, 37, 127, 138, 109, 5, 224, 141, 149, 34, 249, 220, 19, 139, 66, 172, 175, 78, 144, 83, 62, 42, 62, 236, 188, 2, 17, 0, 0, 0, 4, 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