Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fcf166bfba9b2af2393f58c43614f4c682e01ac2a1f5d7a3f74a800b33ed346

Tx prefix hash: 0e0c41f0c5a92ece1fbf3892c2d042426098251125414cc6a97393a966dc58f3
Tx public key: eaa7bfe546c4a08ba76fa971673e3b0f06f8e54b2d474e128f2011382d15c456
Timestamp: 1702354685 Timestamp [UCT]: 2023-12-12 04:18:05 Age [y:d:h:m:s]: 01:327:07:24:58
Block: 911258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492778 RingCT/type: yes/0
Extra: 01eaa7bfe546c4a08ba76fa971673e3b0f06f8e54b2d474e128f2011382d15c456021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0ab707ed29f0143146932e38f4cd77d4ac5cda6afcd7c55c32a9c261b384e4d 0.600000000000 1368439 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": 911268, "vin": [ { "gen": { "height": 911258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0ab707ed29f0143146932e38f4cd77d4ac5cda6afcd7c55c32a9c261b384e4d" } } ], "extra": [ 1, 234, 167, 191, 229, 70, 196, 160, 139, 167, 111, 169, 113, 103, 62, 59, 15, 6, 248, 229, 75, 45, 71, 78, 18, 143, 32, 17, 56, 45, 21, 196, 86, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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