Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e151147e2cb2d375a701d11028964fa963947edc84d48cf18ccb0e86bdfb0c8

Tx prefix hash: 2203fc7a87dc8fa14eb20d64a417cad17e329ec28044816bab3de1a44cd6620a
Tx public key: 615d0c5e9b77ff3c88c75a29a9c1824b9d870ae8650b7109b4a8dfb2861974d3
Timestamp: 1722316985 Timestamp [UCT]: 2024-07-30 05:23:05 Age [y:d:h:m:s]: 00:320:00:04:47
Block: 1076766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228557 RingCT/type: yes/0
Extra: 01615d0c5e9b77ff3c88c75a29a9c1824b9d870ae8650b7109b4a8dfb2861974d302110000000194f0f54f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24f73f39d30e93f56651da144d15378567f8918e7ccc1ec3f41c805beeb96a69 0.600000000000 1549307 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": 1076776, "vin": [ { "gen": { "height": 1076766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24f73f39d30e93f56651da144d15378567f8918e7ccc1ec3f41c805beeb96a69" } } ], "extra": [ 1, 97, 93, 12, 94, 155, 119, 255, 60, 136, 199, 90, 41, 169, 193, 130, 75, 157, 135, 10, 232, 101, 11, 113, 9, 180, 168, 223, 178, 134, 25, 116, 211, 2, 17, 0, 0, 0, 1, 148, 240, 245, 79, 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