Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6c2a31060494776c21ce8dfcf782df6d12310e34e7dd9ee689d93ce6417d06a

Tx prefix hash: 1afbfa688c71750adb6679057a3a31b7e137e1f7da9fff2de0c58ef35e27f7d8
Tx public key: fb73d2b424c719e54896f47e3665d394f2159238a3dc9fe9b12215e49fe7fb43
Timestamp: 1703332662 Timestamp [UCT]: 2023-12-23 11:57:42 Age [y:d:h:m:s]: 01:321:12:55:56
Block: 919371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488643 RingCT/type: yes/0
Extra: 01fb73d2b424c719e54896f47e3665d394f2159238a3dc9fe9b12215e49fe7fb4302110000000246113aa8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f22f5c6ea1348af4aded78b67f3e1eec806ef8cbce009e41abc15f0ee22791 0.600000000000 1377043 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": 919381, "vin": [ { "gen": { "height": 919371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f22f5c6ea1348af4aded78b67f3e1eec806ef8cbce009e41abc15f0ee22791" } } ], "extra": [ 1, 251, 115, 210, 180, 36, 199, 25, 229, 72, 150, 244, 126, 54, 101, 211, 148, 242, 21, 146, 56, 163, 220, 159, 233, 177, 34, 21, 228, 159, 231, 251, 67, 2, 17, 0, 0, 0, 2, 70, 17, 58, 168, 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