Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fca23b1960d0780ea5f1d6d271fdbf57490ece8390fd4870489b01ed5d1673c0

Tx prefix hash: b6a9aefc7eff66228c0de0b75f964ab4c0f40f19e458dcd501059f46bae4651b
Tx public key: ab9ca051f5e75ab20930e9762acbefdcf45259b73ac3a731c229a6569e944d5b
Timestamp: 1710021744 Timestamp [UCT]: 2024-03-09 22:02:24 Age [y:d:h:m:s]: 01:047:21:02:57
Block: 974836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295232 RingCT/type: yes/0
Extra: 01ab9ca051f5e75ab20930e9762acbefdcf45259b73ac3a731c229a6569e944d5b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2ea65ed148365070c8e299e8c4383e067872e314113001b0a8a3512c96903e7 0.600000000000 1434803 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": 974846, "vin": [ { "gen": { "height": 974836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2ea65ed148365070c8e299e8c4383e067872e314113001b0a8a3512c96903e7" } } ], "extra": [ 1, 171, 156, 160, 81, 245, 231, 90, 178, 9, 48, 233, 118, 42, 203, 239, 220, 244, 82, 89, 183, 58, 195, 167, 49, 194, 41, 166, 86, 158, 148, 77, 91, 2, 17, 0, 0, 0, 1, 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