Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 951cf51a161deee78640a63f2ce74d51728c8033c41b46c4eb133eb0bad24054

Tx prefix hash: bbc2a2d133df6f16325784bf40b9597c906e3dbef1b7ea593e0b9e0d4fb9f36a
Tx public key: 1e8d522639f08bba6c047e00b84de82ee0b57c2cf0eed85a0d751f6f6c2ed270
Timestamp: 1676281730 Timestamp [UCT]: 2023-02-13 09:48:50 Age [y:d:h:m:s]: 02:012:19:33:51
Block: 695999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530719 RingCT/type: yes/0
Extra: 011e8d522639f08bba6c047e00b84de82ee0b57c2cf0eed85a0d751f6f6c2ed27002110000000175e3f0e9000000000000000000

1 output(s) for total of 3.032957392000 dcy

stealth address amount amount idx
00: f6891b404a6f1667d323df028bd176be77788a025ae112c3dc5b6a74231a5bb1 3.032957392000 1138964 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": 696009, "vin": [ { "gen": { "height": 695999 } } ], "vout": [ { "amount": 3032957392, "target": { "key": "f6891b404a6f1667d323df028bd176be77788a025ae112c3dc5b6a74231a5bb1" } } ], "extra": [ 1, 30, 141, 82, 38, 57, 240, 139, 186, 108, 4, 126, 0, 184, 77, 232, 46, 224, 181, 124, 44, 240, 238, 216, 90, 13, 117, 31, 111, 108, 46, 210, 112, 2, 17, 0, 0, 0, 1, 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