Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac849f88c303614b664f04ddd3bd8e0baa6e38a31a4c32349fa75133da2c9cc

Tx prefix hash: 92485ff5830f8e59c49737a5614cdcdf6d33f3e72139983fffdce17ce42d7a39
Tx public key: 6610fcd40c2ac662238e0b1d43792a6f5fdaacbbb4687bcf8fe363ab3a111e1e
Timestamp: 1761878284 Timestamp [UCT]: 2025-10-31 02:38:04 Age [y:d:h:m:s]: 00:008:00:57:22
Block: 1401634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5748 RingCT/type: yes/0
Extra: 016610fcd40c2ac662238e0b1d43792a6f5fdaacbbb4687bcf8fe363ab3a111e1e0211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e395b65dd1d664a230a319ab473dc9f06a2df3c93e1f4ec80bdc8ca3fef089d 0.600000000000 1889953 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": 1401644, "vin": [ { "gen": { "height": 1401634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e395b65dd1d664a230a319ab473dc9f06a2df3c93e1f4ec80bdc8ca3fef089d" } } ], "extra": [ 1, 102, 16, 252, 212, 12, 42, 198, 98, 35, 142, 11, 29, 67, 121, 42, 111, 95, 218, 172, 187, 180, 104, 123, 207, 143, 227, 99, 171, 58, 17, 30, 30, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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