Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0744ecdb9f6a5fa3e2e7794d28b633784b3c93541bceaa1474c92d5420e1cec

Tx prefix hash: 948a6bc8c2d8b8acdad98fa7c3c8e6c9e8d5a5f22b43050b5492e84087397aca
Tx public key: cafb24f817979f3fe1b209a3a1d6fde9f99e173a8c351c2ae81b626a3c9101ff
Timestamp: 1748301643 Timestamp [UCT]: 2025-05-26 23:20:43 Age [y:d:h:m:s]: 00:226:13:39:01
Block: 1291658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159688 RingCT/type: yes/0
Extra: 01cafb24f817979f3fe1b209a3a1d6fde9f99e173a8c351c2ae81b626a3c9101ff02110000000886ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e4136c77ac65e4512dac31e50617affff24cd2092e491ffc0c2a8a3ad9c1804 0.600000000000 1779129 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": 1291668, "vin": [ { "gen": { "height": 1291658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e4136c77ac65e4512dac31e50617affff24cd2092e491ffc0c2a8a3ad9c1804" } } ], "extra": [ 1, 202, 251, 36, 248, 23, 151, 159, 63, 225, 178, 9, 163, 161, 214, 253, 233, 249, 158, 23, 58, 140, 53, 28, 42, 232, 27, 98, 106, 60, 145, 1, 255, 2, 17, 0, 0, 0, 8, 134, 174, 47, 13, 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