Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a2cc3c79ffdd846a83f5d38442902269570c157da2e6e76fcb2f939fb8b7ca3

Tx prefix hash: 5efe1a0c1ec1aef0c66f3a7202fc483f06e85fa684b82247983b8cccdd29405f
Tx public key: f8844a35a7dd939c4b83aff63d0bc72ceb2b3ff87029139c0469994ce2a3cebb
Timestamp: 1707393927 Timestamp [UCT]: 2024-02-08 12:05:27 Age [y:d:h:m:s]: 01:277:21:46:09
Block: 953032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457400 RingCT/type: yes/0
Extra: 01f8844a35a7dd939c4b83aff63d0bc72ceb2b3ff87029139c0469994ce2a3cebb021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41fb0dc9ba660a4676a9b544d086356aee2e3cc44119c939144d543b29ce2238 0.600000000000 1412192 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": 953042, "vin": [ { "gen": { "height": 953032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41fb0dc9ba660a4676a9b544d086356aee2e3cc44119c939144d543b29ce2238" } } ], "extra": [ 1, 248, 132, 74, 53, 167, 221, 147, 156, 75, 131, 175, 246, 61, 11, 199, 44, 235, 43, 63, 248, 112, 41, 19, 156, 4, 105, 153, 76, 226, 163, 206, 187, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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