Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f74f8de278dc84ec119aa070b1ba7b2cc7192c2f64c6e1e098e0006120cf23ba

Tx prefix hash: 5439257110abf27f1e1916066eaf5a68573d2951d1fb4b57272ec9f00d517997
Tx public key: 16dc1a74f2c4bef055b506331cf6f1180ac20e031745f9933aee1c5c9fe4d015
Timestamp: 1674730213 Timestamp [UCT]: 2023-01-26 10:50:13 Age [y:d:h:m:s]: 02:072:23:11:44
Block: 683119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573781 RingCT/type: yes/0
Extra: 0116dc1a74f2c4bef055b506331cf6f1180ac20e031745f9933aee1c5c9fe4d0150211000000015029cbac000000000000000000

1 output(s) for total of 3.346132351000 dcy

stealth address amount amount idx
00: df4d170aa0ae141365ae2ae97007e9d8fde155bd8febdcc5ddfd93496ecea737 3.346132351000 1125290 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": 683129, "vin": [ { "gen": { "height": 683119 } } ], "vout": [ { "amount": 3346132351, "target": { "key": "df4d170aa0ae141365ae2ae97007e9d8fde155bd8febdcc5ddfd93496ecea737" } } ], "extra": [ 1, 22, 220, 26, 116, 242, 196, 190, 240, 85, 181, 6, 51, 28, 246, 241, 24, 10, 194, 14, 3, 23, 69, 249, 147, 58, 238, 28, 92, 159, 228, 208, 21, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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