Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a264d9a2ed080b6a1cc27a3c680b9e6a3d394400f7663da7a4b4c60f449e1f15

Tx prefix hash: 99cd59443fd960a622277b10b8c05cc886563f0b8a16710ed86a2e4928431feb
Tx public key: 86704ac5afee61020f7f9b78f7082fcf1d9bacc0d17720cb6deb2fc4eea66a9c
Timestamp: 1752470460 Timestamp [UCT]: 2025-07-14 05:21:00 Age [y:d:h:m:s]: 00:179:03:05:53
Block: 1325093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126835 RingCT/type: yes/0
Extra: 0186704ac5afee61020f7f9b78f7082fcf1d9bacc0d17720cb6deb2fc4eea66a9c021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 431769a847e458c07112330c3c224a97734e842513614ebf7e3bcc480219ff05 0.600000000000 1812838 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": 1325103, "vin": [ { "gen": { "height": 1325093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "431769a847e458c07112330c3c224a97734e842513614ebf7e3bcc480219ff05" } } ], "extra": [ 1, 134, 112, 74, 197, 175, 238, 97, 2, 15, 127, 155, 120, 247, 8, 47, 207, 29, 155, 172, 192, 209, 119, 32, 203, 109, 235, 47, 196, 238, 166, 106, 156, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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