Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86bca18332028c284d233400d2a0f54bf9b9ce30e61604e79adc768c75a5c024

Tx prefix hash: 877288dbbad85bead9f660eba71c79cc92b933424a5f13746a198df1e18902bd
Tx public key: 6ec711c3fe2d879e43b907efc6b1748ebcd71b44522e159adb371002d7f3f9c5
Timestamp: 1706182184 Timestamp [UCT]: 2024-01-25 11:29:44 Age [y:d:h:m:s]: 01:033:07:23:10
Block: 942969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284871 RingCT/type: yes/0
Extra: 016ec711c3fe2d879e43b907efc6b1748ebcd71b44522e159adb371002d7f3f9c50211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84ff173382f0fb8bb79027932a9f0ead763f23f0acaebdb994e54198d6d92df4 0.600000000000 1401162 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": 942979, "vin": [ { "gen": { "height": 942969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84ff173382f0fb8bb79027932a9f0ead763f23f0acaebdb994e54198d6d92df4" } } ], "extra": [ 1, 110, 199, 17, 195, 254, 45, 135, 158, 67, 185, 7, 239, 198, 177, 116, 142, 188, 215, 27, 68, 82, 46, 21, 154, 219, 55, 16, 2, 215, 243, 249, 197, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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