Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af342029bc2e138c61cd57e11692fd200ff9632216b76ec2246944c6fb141ff1

Tx prefix hash: 389e6f5239b18a35a5aa9d3d1680ca341e95eff7ab9b6e8378149e053edf41fa
Tx public key: a3bafd49e25de65ef8b8a7fa9efd15238d165393db1fc46622b7e91e6322e44b
Timestamp: 1702862229 Timestamp [UCT]: 2023-12-18 01:17:09 Age [y:d:h:m:s]: 02:046:17:40:54
Block: 915473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553052 RingCT/type: yes/0
Extra: 01a3bafd49e25de65ef8b8a7fa9efd15238d165393db1fc46622b7e91e6322e44b02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f983a5e319dcfa6a0c0d33d984489ddc3a913e3870bd2e0ed43f58c65fa725b5 0.600000000000 1372869 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": 915483, "vin": [ { "gen": { "height": 915473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f983a5e319dcfa6a0c0d33d984489ddc3a913e3870bd2e0ed43f58c65fa725b5" } } ], "extra": [ 1, 163, 186, 253, 73, 226, 93, 230, 94, 248, 184, 167, 250, 158, 253, 21, 35, 141, 22, 83, 147, 219, 31, 196, 102, 34, 183, 233, 30, 99, 34, 228, 75, 2, 17, 0, 0, 0, 7, 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