Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 354f4b4512858c61b7b32222c004ed8f6575f5d9de261262d232d110ea838b8b

Tx prefix hash: e4d39d133eccefe1330a0a5b62cde5e51b4340c7386a92dd6189aafee596319d
Tx public key: 1aa70e09d7af7747df752372ad6a713f6a28f687065bf32e94b4d4679b632087
Timestamp: 1702201405 Timestamp [UCT]: 2023-12-10 09:43:25 Age [y:d:h:m:s]: 01:112:12:26:41
Block: 910004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341548 RingCT/type: yes/0
Extra: 011aa70e09d7af7747df752372ad6a713f6a28f687065bf32e94b4d4679b63208702110000000d33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d951f8c87deeaff06e803889afa2cbd93a3520f92fcd3f015f0d2ec72f2fa89b 0.600000000000 1367143 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": 910014, "vin": [ { "gen": { "height": 910004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d951f8c87deeaff06e803889afa2cbd93a3520f92fcd3f015f0d2ec72f2fa89b" } } ], "extra": [ 1, 26, 167, 14, 9, 215, 175, 119, 71, 223, 117, 35, 114, 173, 106, 113, 63, 106, 40, 246, 135, 6, 91, 243, 46, 148, 180, 212, 103, 155, 99, 32, 135, 2, 17, 0, 0, 0, 13, 51, 175, 153, 244, 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