Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 472c23bf1d96a659a434397e95bb519d725e2d3b43cc666d672a4f6fe6c9b2b3

Tx prefix hash: fa4d91655ee503a48d667f4ad1b0a98a47b2d93093fb2c0c5b1551d5b5e756d5
Tx public key: 39713d6adc9428bd2ee8e7a299306f39ad14dc6b7ead34650a131c682a31d0b5
Timestamp: 1743155615 Timestamp [UCT]: 2025-03-28 09:53:35 Age [y:d:h:m:s]: 00:236:04:21:16
Block: 1249036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166535 RingCT/type: yes/0
Extra: 0139713d6adc9428bd2ee8e7a299306f39ad14dc6b7ead34650a131c682a31d0b5021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2daf745aa64c92fe621dc89cdf7849812b2af4f66b5219b28b0e9e8a6fd5cae7 0.600000000000 1736071 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": 1249046, "vin": [ { "gen": { "height": 1249036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2daf745aa64c92fe621dc89cdf7849812b2af4f66b5219b28b0e9e8a6fd5cae7" } } ], "extra": [ 1, 57, 113, 61, 106, 220, 148, 40, 189, 46, 232, 231, 162, 153, 48, 111, 57, 173, 20, 220, 107, 126, 173, 52, 101, 10, 19, 28, 104, 42, 49, 208, 181, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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