Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 435493c55a3e95f99f072b464046606b03a042974f68a20d807c22c1b4f92fdc

Tx prefix hash: 80b83348bc22bf220e456444046550f3e93efde2a2cc90a27220581b2ef193a6
Tx public key: 5c7e0408f5c576cafa7d4d3ee0ebcf54e368b10cd4c643b25510d7ccd362e9fd
Timestamp: 1652203269 Timestamp [UCT]: 2022-05-10 17:21:09 Age [y:d:h:m:s]: 03:174:16:59:01
Block: 498133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 903738 RingCT/type: yes/0
Extra: 015c7e0408f5c576cafa7d4d3ee0ebcf54e368b10cd4c643b25510d7ccd362e9fd021100000006a8c141c5000000000000000000

1 output(s) for total of 13.723939486000 dcy

stealth address amount amount idx
00: 0cf9ed9f20fdcbfd696efc2db3fe5c22a9e55e260a44be21b9180f2ba78975a4 13.723939486000 922300 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": 498143, "vin": [ { "gen": { "height": 498133 } } ], "vout": [ { "amount": 13723939486, "target": { "key": "0cf9ed9f20fdcbfd696efc2db3fe5c22a9e55e260a44be21b9180f2ba78975a4" } } ], "extra": [ 1, 92, 126, 4, 8, 245, 197, 118, 202, 250, 125, 77, 62, 224, 235, 207, 84, 227, 104, 177, 12, 212, 198, 67, 178, 85, 16, 215, 204, 211, 98, 233, 253, 2, 17, 0, 0, 0, 6, 168, 193, 65, 197, 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