Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471b0814cacaee25149c57a06e96da0c5b4ef1a2713328bbc31a469bbfb567a4

Tx prefix hash: d8613599ccb12de3ae6eb85f2590ba48dea212436a4e903ea4a2af0bd8403429
Tx public key: 3a26c44cedf9f3b48cf12822954daf9f1f5de103b9d173f88d1b75b6c7332141
Timestamp: 1715773095 Timestamp [UCT]: 2024-05-15 11:38:15 Age [y:d:h:m:s]: 01:177:15:36:14
Block: 1022516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385568 RingCT/type: yes/0
Extra: 013a26c44cedf9f3b48cf12822954daf9f1f5de103b9d173f88d1b75b6c73321410211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fe2ad63de59afa0689ece1c51721cf57b3688895f8dbe8b2d50b2230e6c3a2d 0.600000000000 1487143 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": 1022526, "vin": [ { "gen": { "height": 1022516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fe2ad63de59afa0689ece1c51721cf57b3688895f8dbe8b2d50b2230e6c3a2d" } } ], "extra": [ 1, 58, 38, 196, 76, 237, 249, 243, 180, 140, 241, 40, 34, 149, 77, 175, 159, 31, 93, 225, 3, 185, 209, 115, 248, 141, 27, 117, 182, 199, 51, 33, 65, 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