Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2911aa4ecb2a3bb9bf7afb48413b2ac038fb0d59512c254a83c8ee5cf5f4421

Tx prefix hash: 0ba52b7edd5f1050cadf2760155583e35ba493467938a20b492fb3a57073bebb
Tx public key: 4f523ffdcfd530861faba88a542b99b68d8754e585e3e66841fa7b4c2dede8b6
Timestamp: 1699567510 Timestamp [UCT]: 2023-11-09 22:05:10 Age [y:d:h:m:s]: 01:184:11:04:16
Block: 888164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393039 RingCT/type: yes/0
Extra: 014f523ffdcfd530861faba88a542b99b68d8754e585e3e66841fa7b4c2dede8b6021100000005faf35c9c000000000000000000

1 output(s) for total of 0.700074041000 dcy

stealth address amount amount idx
00: b7a0beccc2b49a263a9a4e1edd506378e1fd9d23bb884f7b3a61f710767010a9 0.700074041000 1344093 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": 888174, "vin": [ { "gen": { "height": 888164 } } ], "vout": [ { "amount": 700074041, "target": { "key": "b7a0beccc2b49a263a9a4e1edd506378e1fd9d23bb884f7b3a61f710767010a9" } } ], "extra": [ 1, 79, 82, 63, 253, 207, 213, 48, 134, 31, 171, 168, 138, 84, 43, 153, 182, 141, 135, 84, 229, 133, 227, 230, 104, 65, 250, 123, 76, 45, 237, 232, 182, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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