Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349abd321a648d54ed958c1cc444831f89a4bb46435c03df2b835b1d700cbe35

Tx prefix hash: dd50e000afa67b3825cb5d093d1b889029766f7c6ca3aa905401991b36539d90
Tx public key: d8e16c6bac88e8e507917afdedc3ad83023fbdec0c775b410cf18a7d06fd0f5d
Timestamp: 1701814248 Timestamp [UCT]: 2023-12-05 22:10:48 Age [y:d:h:m:s]: 01:180:04:45:09
Block: 906784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389992 RingCT/type: yes/0
Extra: 01d8e16c6bac88e8e507917afdedc3ad83023fbdec0c775b410cf18a7d06fd0f5d02110000000133af99f4000000000000000000

1 output(s) for total of 0.607362757000 dcy

stealth address amount amount idx
00: d77e94adecce8093fa5637533781942faad14821c68c685dea09783975dd9ae7 0.607362757000 1363743 of 0

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": 906794, "vin": [ { "gen": { "height": 906784 } } ], "vout": [ { "amount": 607362757, "target": { "key": "d77e94adecce8093fa5637533781942faad14821c68c685dea09783975dd9ae7" } } ], "extra": [ 1, 216, 225, 108, 107, 172, 136, 232, 229, 7, 145, 122, 253, 237, 195, 173, 131, 2, 63, 189, 236, 12, 119, 91, 65, 12, 241, 138, 125, 6, 253, 15, 93, 2, 17, 0, 0, 0, 1, 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