Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28587807d1716bade7dd886a4d917fa41aaa48fead01888ad80f76f0610d2f30

Tx prefix hash: 41beb10b88e07c0d1753a1a4d11bbca227b7b83cf84759f32a9641188fe3f932
Tx public key: 4d1b79dc9a6df105579c36e979b3263600cd6fa667ef57f57b1d39b6124fd8fb
Timestamp: 1707717176 Timestamp [UCT]: 2024-02-12 05:52:56 Age [y:d:h:m:s]: 00:315:00:10:42
Block: 955716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225557 RingCT/type: yes/0
Extra: 014d1b79dc9a6df105579c36e979b3263600cd6fa667ef57f57b1d39b6124fd8fb0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4487d2959001a802648bc0ed2f22b178d8750ae50c8835d690218a68ad8d16f1 0.600000000000 1415014 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": 955726, "vin": [ { "gen": { "height": 955716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4487d2959001a802648bc0ed2f22b178d8750ae50c8835d690218a68ad8d16f1" } } ], "extra": [ 1, 77, 27, 121, 220, 154, 109, 241, 5, 87, 156, 54, 233, 121, 179, 38, 54, 0, 205, 111, 166, 103, 239, 87, 245, 123, 29, 57, 182, 18, 79, 216, 251, 2, 17, 0, 0, 0, 5, 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