Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fcda4c6a4ef59bdb9e2fafe0125d1cc0a36c565f7e6dc8af9279d7f6f4a6c47

Tx prefix hash: 53b306dbe3a6753cf0eb42ea7e223019f241af00035a0ae55876f7034f560ff9
Tx public key: aaa8d6be301f678a89106d6b8f409c88f8e8af00e28114a27091b17d9b35e866
Timestamp: 1764041039 Timestamp [UCT]: 2025-11-25 03:23:59 Age [y:d:h:m:s]: 00:002:06:45:12
Block: 1419554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1628 RingCT/type: yes/0
Extra: 01aaa8d6be301f678a89106d6b8f409c88f8e8af00e28114a27091b17d9b35e86602110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ae2fece23a1004db05b68ca2c980090e10f6776364f8ba2af474b8efcc8b343 0.600000000000 1908091 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": 1419564, "vin": [ { "gen": { "height": 1419554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ae2fece23a1004db05b68ca2c980090e10f6776364f8ba2af474b8efcc8b343" } } ], "extra": [ 1, 170, 168, 214, 190, 48, 31, 103, 138, 137, 16, 109, 107, 143, 64, 156, 136, 248, 232, 175, 0, 226, 129, 20, 162, 112, 145, 177, 125, 155, 53, 232, 102, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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