Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0bc40b0d6ed4aeaf45e74256833a28e08e2f2a9917050e4b8839fa72d9c2c88

Tx prefix hash: 8bb133be15f25337b0029bc27876543d44cd30afeb264ae2db814a63d1dc69c6
Tx public key: 0b27a364b14b15a1c8ce6364adf51a1e2429059fb17ab1051723870545b27c6f
Timestamp: 1702428970 Timestamp [UCT]: 2023-12-13 00:56:10 Age [y:d:h:m:s]: 01:333:16:25:35
Block: 911900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497322 RingCT/type: yes/0
Extra: 010b27a364b14b15a1c8ce6364adf51a1e2429059fb17ab1051723870545b27c6f02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f35716f8a1588c2fca5acb514fdf012d265b5155fd8dc876ab43d7bc9c73f65a 0.600000000000 1369116 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": 911910, "vin": [ { "gen": { "height": 911900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f35716f8a1588c2fca5acb514fdf012d265b5155fd8dc876ab43d7bc9c73f65a" } } ], "extra": [ 1, 11, 39, 163, 100, 177, 75, 21, 161, 200, 206, 99, 100, 173, 245, 26, 30, 36, 41, 5, 159, 177, 122, 177, 5, 23, 35, 135, 5, 69, 178, 124, 111, 2, 17, 0, 0, 0, 8, 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