Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acf7fdcd1a82855e66d7d9a5b71235cb0aa82f570ac5449e315e9d320cb4c1e5

Tx prefix hash: 57ad4d2b2c7e4fdc5a347f3d7fa8d2716aa67a52e5cfaf1e08b33b01d03e4a8d
Tx public key: 6ea7930e0b1142b6c96763ac1cc55a0beccc5b6e35ac0fe9f7d50351d52cdbf2
Timestamp: 1727030578 Timestamp [UCT]: 2024-09-22 18:42:58 Age [y:d:h:m:s]: 00:062:21:08:27
Block: 1115841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44954 RingCT/type: yes/0
Extra: 016ea7930e0b1142b6c96763ac1cc55a0beccc5b6e35ac0fe9f7d50351d52cdbf2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0626901fc6992704022624099e11ece33596d39ddd3feb53262f13193822cd2 0.600000000000 1596114 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": 1115851, "vin": [ { "gen": { "height": 1115841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0626901fc6992704022624099e11ece33596d39ddd3feb53262f13193822cd2" } } ], "extra": [ 1, 110, 167, 147, 14, 11, 17, 66, 182, 201, 103, 99, 172, 28, 197, 90, 11, 236, 204, 91, 110, 53, 172, 15, 233, 247, 213, 3, 81, 213, 44, 219, 242, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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