Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2663987d92896eb2b7de1349cac6dcb69a034963d376ee2bfaf4d1b8d06b47

Tx prefix hash: 42c32e0bc771512547ddcdaa7946f41c1dcb13136299591b95a93e8b760d37ef
Tx public key: 88efcb72584e15984869e24c3b405d038791588b1be812b53cf9c866d9b12729
Timestamp: 1729182034 Timestamp [UCT]: 2024-10-17 16:20:34 Age [y:d:h:m:s]: 01:024:08:52:53
Block: 1133681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275771 RingCT/type: yes/0
Extra: 0188efcb72584e15984869e24c3b405d038791588b1be812b53cf9c866d9b12729021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ad21a9374f6ae4c2b1bd85b3d693e6a1f75e2eec141e0493f61100e4efca7b5 0.600000000000 1616864 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": 1133691, "vin": [ { "gen": { "height": 1133681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ad21a9374f6ae4c2b1bd85b3d693e6a1f75e2eec141e0493f61100e4efca7b5" } } ], "extra": [ 1, 136, 239, 203, 114, 88, 78, 21, 152, 72, 105, 226, 76, 59, 64, 93, 3, 135, 145, 88, 139, 27, 232, 18, 181, 60, 249, 200, 102, 217, 177, 39, 41, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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