Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fbe136bfbcc57f200306b54e7af1b3539e7690f1c746c72963f6f80484b46ba

Tx prefix hash: c7700c87295ba2678cf52ab1b2cf8ab7a56b327c906717e25c337fbf61e2354c
Tx public key: 418ce8e558f084b3d93cb67cd945f1b20acda5afbfcbc3b8fae315a9d288b97f
Timestamp: 1711108539 Timestamp [UCT]: 2024-03-22 11:55:39 Age [y:d:h:m:s]: 01:200:08:52:32
Block: 983862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401826 RingCT/type: yes/0
Extra: 01418ce8e558f084b3d93cb67cd945f1b20acda5afbfcbc3b8fae315a9d288b97f0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1114bead0af70633f2adff4e560d7e51701587b1f864368d658c280d0ef01a6 0.600000000000 1444015 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": 983872, "vin": [ { "gen": { "height": 983862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1114bead0af70633f2adff4e560d7e51701587b1f864368d658c280d0ef01a6" } } ], "extra": [ 1, 65, 140, 232, 229, 88, 240, 132, 179, 217, 60, 182, 124, 217, 69, 241, 178, 10, 205, 165, 175, 191, 203, 195, 184, 250, 227, 21, 169, 210, 136, 185, 127, 2, 17, 0, 0, 0, 8, 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