Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dd1a13b03fb97ab86301c7249a7ab003bf97dc2d28964a2110f3b8cf51b2612

Tx prefix hash: 016b319cec89dfbd2475d6ade7bfdd0f5dbf81f8fe350f0429025ec00c2ac950
Tx public key: fb3eaa08330049a83f9b6c5bb8007408b2c42dfa14bbd1845ce194770d5feca4
Timestamp: 1681925133 Timestamp [UCT]: 2023-04-19 17:25:33 Age [y:d:h:m:s]: 02:039:10:30:29
Block: 742139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550361 RingCT/type: yes/0
Extra: 01fb3eaa08330049a83f9b6c5bb8007408b2c42dfa14bbd1845ce194770d5feca402110000000175e3f0e9000000000000000000

1 output(s) for total of 2.132974341000 dcy

stealth address amount amount idx
00: 1d334416c04bf6edc73f94da31aa8df642b0a425fa9e0ab13321c0697cf0ff4d 2.132974341000 1189096 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": 742149, "vin": [ { "gen": { "height": 742139 } } ], "vout": [ { "amount": 2132974341, "target": { "key": "1d334416c04bf6edc73f94da31aa8df642b0a425fa9e0ab13321c0697cf0ff4d" } } ], "extra": [ 1, 251, 62, 170, 8, 51, 0, 73, 168, 63, 155, 108, 91, 184, 0, 116, 8, 178, 196, 45, 250, 20, 187, 209, 132, 92, 225, 148, 119, 13, 95, 236, 164, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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