Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7c695f8694f5b9c342eb57985cb93f8509bb9b45a82d49cab0591ae12601747

Tx prefix hash: b883651aacbad177258d6d8a9acd721bb7f46a86c515dc5d168522ed27da13e0
Tx public key: d3fb9569ac978d0d8a8fe284444e45c9b331e0471096f9097c758c976a36c94a
Timestamp: 1699804760 Timestamp [UCT]: 2023-11-12 15:59:20 Age [y:d:h:m:s]: 01:149:17:59:54
Block: 890135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368206 RingCT/type: yes/0
Extra: 01d3fb9569ac978d0d8a8fe284444e45c9b331e0471096f9097c758c976a36c94a021100000004073143b5000000000000000000

1 output(s) for total of 0.689625370000 dcy

stealth address amount amount idx
00: f6908e7be476cc0b22ec4688ed9efd37fd9c29f0dac9f056a3ec7c25ff63b647 0.689625370000 1346154 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": 890145, "vin": [ { "gen": { "height": 890135 } } ], "vout": [ { "amount": 689625370, "target": { "key": "f6908e7be476cc0b22ec4688ed9efd37fd9c29f0dac9f056a3ec7c25ff63b647" } } ], "extra": [ 1, 211, 251, 149, 105, 172, 151, 141, 13, 138, 143, 226, 132, 68, 78, 69, 201, 179, 49, 224, 71, 16, 150, 249, 9, 124, 117, 140, 151, 106, 54, 201, 74, 2, 17, 0, 0, 0, 4, 7, 49, 67, 181, 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