Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0fe24b486fdc1d6cf0a003dc687fde139a3e5fe8bccf66271dd9b0482455d4e

Tx prefix hash: 47c612f620cce1f35e2654c4bc09dd3543d5248f78076c32cba1d550a6a4d1c7
Tx public key: 58683107ad184d94f1d32527476e9ac3e341c97a2e02427eca49e52d3591a31f
Timestamp: 1582964461 Timestamp [UCT]: 2020-02-29 08:21:01 Age [y:d:h:m:s]: 04:320:16:39:51
Block: 73830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122996 RingCT/type: yes/0
Extra: 0158683107ad184d94f1d32527476e9ac3e341c97a2e02427eca49e52d3591a31f02110000001d56c366d3000000000000000000

1 output(s) for total of 349.446799410000 dcy

stealth address amount amount idx
00: f57fcffe8bc77156537d5ed43660de16398984ac9151e6a69bab36cbec82d59d 349.446799410000 136390 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": 73840, "vin": [ { "gen": { "height": 73830 } } ], "vout": [ { "amount": 349446799410, "target": { "key": "f57fcffe8bc77156537d5ed43660de16398984ac9151e6a69bab36cbec82d59d" } } ], "extra": [ 1, 88, 104, 49, 7, 173, 24, 77, 148, 241, 211, 37, 39, 71, 110, 154, 195, 227, 65, 201, 122, 46, 2, 66, 126, 202, 73, 229, 45, 53, 145, 163, 31, 2, 17, 0, 0, 0, 29, 86, 195, 102, 211, 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