Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17c1060d232a3c74ce1e080efbc154cce4a8fbf2f64a68fe64efc806de92b53e

Tx prefix hash: 264b45b62cabea60f401bdc603454df206398f32a324dc00740124ef67d0ae03
Tx public key: 1e83de96b70c1da8a44c52dc7dce25da8414d7bae3e1319a87a0a1f8a22b1e54
Timestamp: 1673642798 Timestamp [UCT]: 2023-01-13 20:46:38 Age [y:d:h:m:s]: 02:119:18:37:43
Block: 674087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607298 RingCT/type: yes/0
Extra: 011e83de96b70c1da8a44c52dc7dce25da8414d7bae3e1319a87a0a1f8a22b1e540211000000068b7b6602000000000000000000

1 output(s) for total of 3.584840962000 dcy

stealth address amount amount idx
00: f913b2d8e88d43840294a3b5259e46edce0a8ccbdfd4002d2bdd92fcb2f7162a 3.584840962000 1115726 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": 674097, "vin": [ { "gen": { "height": 674087 } } ], "vout": [ { "amount": 3584840962, "target": { "key": "f913b2d8e88d43840294a3b5259e46edce0a8ccbdfd4002d2bdd92fcb2f7162a" } } ], "extra": [ 1, 30, 131, 222, 150, 183, 12, 29, 168, 164, 76, 82, 220, 125, 206, 37, 218, 132, 20, 215, 186, 227, 225, 49, 154, 135, 160, 161, 248, 162, 43, 30, 84, 2, 17, 0, 0, 0, 6, 139, 123, 102, 2, 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