Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b88c074993dae9869b0a1ecdfa5a4fb8fb2e1c3460c1ee1dc6fa3b8685482b5c

Tx prefix hash: 5ee82934cdea51f41fcadc1e345e5cfe50b1b5aee18c5d2c9e755c34599d2222
Tx public key: 5f65f6c9e9603f680bd8756f957ca6be36d3a11f133208db238ae3e2dce368f7
Timestamp: 1732923887 Timestamp [UCT]: 2024-11-29 23:44:47 Age [y:d:h:m:s]: 00:120:07:56:38
Block: 1164605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85795 RingCT/type: yes/0
Extra: 015f65f6c9e9603f680bd8756f957ca6be36d3a11f133208db238ae3e2dce368f7021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdfb392b7e9bd2f2a69e5e1bd9d29378b1585814c4732c8a5e9e932635f1024c 0.600000000000 1650278 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": 1164615, "vin": [ { "gen": { "height": 1164605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdfb392b7e9bd2f2a69e5e1bd9d29378b1585814c4732c8a5e9e932635f1024c" } } ], "extra": [ 1, 95, 101, 246, 201, 233, 96, 63, 104, 11, 216, 117, 111, 149, 124, 166, 190, 54, 211, 161, 31, 19, 50, 8, 219, 35, 138, 227, 226, 220, 227, 104, 247, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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